Attributing harvest information with unique identifiers

ABSTRACT

Systems and methods allow units of produce to be traced back to the fields in which the produce was grown. In the field, a harvest form is completed with harvest information at the time of the harvest. In some instances, labels having unique codes are used to label the produce in the field, and an additional label is placed on the harvest form to associate a range of unique codes for an entire roll of labels with the harvest information on the form. In the alternative, the label can be read, such as with a hand-held device and associated with harvest information also entered through the hand-held device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a Continuation-In-Part of U.S. patent applicationSer. No. 13/053,200 filed on Mar. 21, 2011 now U.S. Pat. No. 8,342,393and entitled “Attributing Harvest Information with Unique Identifiers”which is a Continuation-In-Part of U.S. patent application Ser. No.12/206,156 filed on Sep. 8, 2008 and also entitled “Attributing HarvestInformation with Unique Identifiers,” now U.S. Pat. No. 7,909,239, whichclaims the benefit of U.S. Provisional Patent Application No. 60/970,933filed on Sep. 7, 2007 and similarly entitled “Attributing HarvestInformation with Unique Identifiers” each of which is incorporatedherein by reference; this application is additionally aContinuation-In-Part of U.S. patent application Ser. No. 13/449,145filed on Apr. 17, 2012 now U.S. Pat. No. 8,286,869 and entitled “CaseLabeling for Field-Packed Produce” which is a Continuation of U.S.patent application Ser. No. 13/221,520 filed on Aug. 30, 2011 and alsoentitled “Case Labeling for Field-Packed Produce,” now U.S. Pat. No.8,196,827, which is a Continuation-In-Part of U.S. patent applicationSer. No. 12/471,201 filed on May 22, 2009 and also entitled “CaseLabeling for Field-Packed Produce,” now U.S. Pat. No. 8,152,063, each ofwhich is further incorporated herein by reference. This application isrelated to U.S. patent application Ser. No. 11/619,747 filed on Jan. 4,2007 and entitled “System and Method of Code Generation andAuthentication,” now U.S. Pat. No. 7,823,768, to U.S. patent applicationSer. No. 11/347,424 filed on Feb. 2, 2006 and entitled “Method andSystem for Deterring Product Counterfeiting, Diversion and Piracy,” nowU.S. Pat. No. 7,614,546, to U.S. patent application Ser. No. 12/054,654filed on Mar. 25, 2008 and entitled “Systems and Methods for AssociatingProduction Attributes with Products,” and also to U.S. Pat. No.7,766,240 filed on Jul. 19, 2008 and entitled “Case-Level TraceabilityWithout the Need for Inline Printing” each of which is incorporatedherein by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates generally to the field of consumer producttraceability, and more specifically to unit-level traceability forproducts such as fresh produce.

2. Description of the Prior Art

When a problem with contaminated food arises, a significant issue isidentifying the source of the contamination. With contaminated produce,being able to quickly identify the growers and the specific fields thatare the source of the contamination is important to enable promptremedial action to protect the public health and to restore publicconfidence in the food supply chain. It is also desirable to be able toeasily identify which produce is affected and which is safe. Restoringpublic confidence and being able to readily identify unaffected producehelp prevent large declines in sales volumes and the unnecessarydestruction of substantial amounts of safe produce.

Presently, the complex and global supply chain makes the process ofidentifying the sources of the contaminated produce slow and cumbersome.

SUMMARY

An exemplary method for associating information with harvested produceis provided. The exemplary method comprises recording harvestinformation on a harvest form, affixing a pair of labels to the harvestform and affixing individual labels to produce being harvested, whereeach of the labels includes a unique code. The method further comprisescreating a record that associates the harvest information with a rangedefined by the unique codes on the pair of labels. In some embodiments,affixing the pair of labels to the harvest form and affixing individuallabels to produce being harvested comprises removing a first label froma roll of labels and affixing the first label to the harvest form,removing the individual labels from the roll after removing the firstlabel and affixing the individual labels to produce being harvested, andafter removing the individual labels from the roll, removing a lastlabel from the roll and affixing the last label to the harvest form.

In various embodiments, produce being harvested comprises bulk looseproduce or item-level packages such as bags, trays, and clamshells. Alsoin various embodiments, the unique codes can comprise cipher texts ofplain text codes, where the plain text codes follow a sequence orpattern. In some of these embodiments, the range defined by the uniquecodes on the pair of labels is a range defined between the plain textcodes corresponding to the unique codes on the pair of labels.

The method can further comprise, in some embodiments, generating a batchof unique codes and producing a set of labels including unique codesfrom the batch, where the set of labels includes the pair of labels andthe individual labels. In some of these embodiments, producing the setof labels comprises creating a roll of the labels. Also in some of theseembodiments, generating the batch of unique codes includes encryptingplain text codes that are related by a sequence or pattern.

In various embodiments the method further comprises marking at least oneof a lot code, a harvest date, or a best before date on at least some ofthe individual labels. Marking can be performed by printing on thelabels either before or after affixing the labels to the produce beingharvested. Printing on every label can be achieved with a printer beforeaffixing the labels, or with a date-coding gun after affixing thelabels, for example. In various embodiments marking the labels includesmarking the lot code and either a harvest date or a best before date,where the combination of the marked lot code and date defines a uniquecode.

Another exemplary method comprises generating a batch of unique codes,marking a plurality of item-level packages with unique codes from thebatch to produce a plurality of marked item-level packages, labeling abox with a unique box code, filling the box with the marked item-levelpackages, and creating a record that associates the unique box code withthe marked item-level packages within the box. Marking the plurality ofitem-level packages can comprise, in some embodiments, affixing a labelto each of the item-level packages, where each label includes a uniquecode from the batch. Marking the plurality of item-level packages canalso comprise printing a unique code from the batch on each item-levelpackage. Labeling the box with the unique box code can include affixinga box label including the unique box code to the box, and in some ofthese embodiments the box label includes one or more detachable tags,each tag including the same unique box code.

Another exemplary method for associating information with harvestedproduce comprises receiving a box including a plurality of markeditem-level packages, each marked item-level package including a uniquecode marked thereon, the box further including a label including aunique box code. The method further comprises recording harvestinformation on a harvest form, packing the marked item-level packageswith produce, and creating a record that associates the harvestinformation with the unique box code. In some embodiments, the labelfurther includes one or more detachable tags, each tag including thesame unique box code. Some of these embodiments further comprisedetaching a detachable tag from the label and affixing the tag to theharvest form.

Still another exemplary method of the invention comprises marking aplurality of item-level packages with unique codes from a batch ofunique codes to produce a plurality of marked and empty item-levelpackages. The method optionally comprises generating the batch of uniquecodes or receiving the batch of unique codes from another party. Theexemplary method further comprises filling a container with the markedand empty item-level packages, and creating a record that associates themarked and empty item-level packages in the container to each other. Invarious embodiments, creating the record that associates the marked andempty item-level packages in the container to each other comprisesscanning one of the marked and empty item-level packages, such as thefirst or last marked and empty item-level package placed into thecontainer.

Yet another exemplary method for associating information with harvestedproduce comprises receiving a container including a plurality of emptyitem-level packages, each empty item-level package including a uniquecode marked thereon, and removing the empty item-level packages from thecontainer and packing the marked item-level packages with produce. Theexemplary method also comprises recording harvest information, such ason a harvest form or with an electronic hand-held device, and creating arecord that associates the harvest information with the unique codesmarked on the item-level packages from the container. Associating theharvest information to the associated marked item-level packagescomprises scanning one of the marked item-level packages, in someembodiments. In various embodiments an item-level package is furtherscanned as part of a labor data collection event. Similarly, a pluralityof item-level packages can be scanned as part of a quality inspectionprocess, and quality assessments are further associated with the harvestinformation.

Yet another exemplary method for associating information with harvestedproduce comprises generating a batch of unique codes with a firstcomputing device, the codes spanning a first range from an initial codeto a final code, and storing the batch of unique codes in a database.The method further comprises transmitting the batch of unique codes to asecond computing device, such as a label printing device, receiving afirst unique code in association with first harvest data from a thirdcomputing device, and storing the first harvest data in association withthe batch of unique codes in the database. The method can optionallycomprise printing a roll of labels, where each label of the roll issequentially printed with a different unique code from the batch, fromthe initial label of the roll with the initial unique code to the finallabel of the roll with the final unique code. In some embodiments, theunique codes are printed on the labels in both a human-readable formatand a machine-readable format. Where a roll of labels is used inconjunction with more than one harvest event, the method can alsofurther comprise receiving a second unique code in association withsecond harvest data from the third computing device, and storing thesecond harvest data in association with the batch of unique codes in thedatabase. In various embodiments transmitting the batch of unique codesto the second computing device is performed over a first communicationchannel and/or receiving the first code in association with the firstharvest data from the third computing device is performed over a secondcommunication channel.

Yet another exemplary method for associating information with harvestedproduce comprises receiving a roll of labels, where each label of theroll sequentially includes a unique code from a batch of unique codes,and the unique codes span a range from an initial unique code to a finalunique code, and an initial label of the roll includes the initialunique code and a final label of the roll includes the final uniquecode. The method further comprises associating first harvest data with afirst unique code from a label of the roll, affixing labels from theroll to item-level packages or individual items of produce, andtransmitting the first unique code in association with the first harvestdata. The label with the first unique code may be the initial label, thefinal label, or any label in between. Associating the first harvest datawith the first unique code can include, in various embodiments, readingthe first unique code with a hand-held device, or affixing a label fromthe roll to a harvest form, the label including the first unique code.The method optionally also comprises associating second harvest datawith a second unique code from the roll, and transmitting the secondunique code in association with the second harvest data.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 shows a pre-printed harvest form according to an exemplaryembodiment of the present invention.

FIG. 2 shows a pre-printed label according to an exemplary embodiment ofthe present invention.

FIG. 3 provides a flowchart representation of a method 300 forassociating information with harvested produce according to an exemplaryembodiment of the present invention.

FIG. 4 illustrates a graphical user interface for entering harvestinformation, according to an exemplary embodiment of the presentinvention.

FIG. 5 provides a flowchart representation of a method for associatinginformation with harvested produce according to an exemplary embodimentof the present invention.

FIG. 6 shows a pre-printed box label according to an exemplaryembodiment of the present invention.

FIG. 7 provides a flowchart representation of another method forassociating information with harvested produce according to an exemplaryembodiment of the present invention.

FIG. 8 provides a flowchart representation of optional steps that can beincluded in either of the exemplary methods provided with respect toFIGS. 5 and 7, according to exemplary embodiments of the presentinvention.

FIG. 9 provides a flowchart representation of a method for associatinginformation with harvested produce according to yet another exemplaryembodiment of the present invention.

FIG. 10 shows a pre-printed label according to another exemplaryembodiment of the present invention.

FIG. 11 shows the pre-printed label of FIG. 10 after further markingthereon, according to another exemplary embodiment of the presentinvention.

FIG. 12 provides a flowchart representation of a method for associatinginformation with harvested produce according to another exemplaryembodiment of the present invention.

FIG. 13 provides a flowchart representation of a method for associatinginformation with harvested produce according to another exemplaryembodiment of the present invention.

FIG. 14 provides a flowchart representation of a method for associatinginformation with harvested produce according to another exemplaryembodiment of the present invention.

FIG. 15 shows a roll of labels according to another exemplary embodimentof the present invention.

FIG. 16 shows a harvest form according to another exemplary embodimentof the present invention.

DETAILED DESCRIPTION OF THE INVENTION

The present disclosure is directed to improving the traceability ofgoods through the supply chain, and in particular, the traceability ofproduce from the field to the consumer. Traceability of produce back tothe growing fields is implemented by marking loose bulk produce,clamshells, bags, boxes, trays, cartons, and other forms of item-levelpackaging with unique codes. The unique codes can follow a knownsequence or pattern, or the unique codes may appear random but areactually the encrypted versions of underlying codes that follow a knownsequence or pattern. Marking can be done with labels that have beenpre-printed with the unique codes, in some instances. Towards the goalof traceability, the unique codes are further associated withinformation such as harvest information. A unique code read from an itemof produce at a later date can be used to find the previously associatedinformation. It will be appreciated that produce is used herein as anexample, but the present invention can equally be applied to other fooditem, pharmaceuticals, and so forth, where it is important to be able totrace units back to their sources.

In the fields where produce is harvested, data entry is not aparticularly convenient task. Accordingly, in some embodiments harvestforms and rolls of labels are provided, where the unique codes on thelabels follow the sequence or pattern. The labels are removed from therolls and applied to the loose bulk produce or item-level packaging, andharvest information is also recorded on the harvest form. Before anyitems are labeled, however, the first label from each roll in use isremoved and placed on the harvest form. When the roll is no longer beingused, for example, because of a harvesting crew change, one final labelis removed from the roll and placed on the harvest form next to thefirst label from that roll. Further embodiments do not require theapplication of the final label to the harvest form. In still furtherembodiments, data entry is performed through a hand-held device, insteadof being recorded on a harvest form, and the same hand-held device isused to read unique codes from labels.

In other embodiments, empty item-level packaging is marked with theunique codes, either by printing, scribing, or with labels, as above. Inthese embodiments, a box filled with these marked item-level packagingis brought to the field and a harvest form is completed. The box, inthese embodiments, includes a label with a unique box code, and in somefurther embodiments the label also includes one or more detachable tags,where each of the tags also includes the same unique box code. Theunique codes marked on the item-level packaging are associated with theunique box code. When the marked item-level packaging from the box arefilled with produce, the unique box code is noted on the harvest form,for example, by detaching a tag from the label on the box and affixedthe tag to the harvest form.

Harvest forms are then brought to a data entry location, such as anoffice, where the information from the harvest forms is used to createelectronic records that are stored in a database, for example. In thoseembodiments that affix pairs of first and last labels to the harvestforms, the unique codes for each pair, or the corresponding underlyingdecrypted codes, are associated with the information from the harvestform. In those embodiments that employ the unique box code, the uniquebox code is associated with the information from the harvest form. Theunique box code provides a link between the records that associate theunique box code with a range of unique codes on item-level packaging andthe further records that associate the unique box code with informationfrom the harvest form. It will be appreciated that performing the dataentry in a centralized location provides several advantages. Forexample, less infrastructure is required, and in particular, fewerscanners. Those scanners, in turn, are not subjected to harsh fieldconditions that tend to cause scanners to have to be replacedprematurely. Centralized data entry, and the methods described hereingenerally, have little impact on the workflow in the fields.

FIG. 1 shows a pre-printed harvest form 100 according to an exemplaryembodiment of the present invention. The harvest form 100 provides aconvenient way to record information in the fields and includes spacesto place labels used for marking individual items of produce, oritem-level packaging such as bags, clamshells, cartons, baskets, and soforth. The harvest form 100 can include various types of information.For example, the harvest form 100 can include information that does notvary from one harvest to another, such as the type of produce—honeydewmelon in the exemplary harvest form 100. Information of this type can bepre-printed on the harvest form 100, in some embodiments.

The harvest form 100 also can include a region 110 for recordinginformation such as the harvest event data for the particular harvest.Additionally, each harvest form 100 includes a unique harvest form code120 that is different for each harvest form 100, in some embodiments.The unique harvest form code 120 can also be pre-printed on the harvestform 100, in some embodiments. The unique harvest form code 120 can alsobe stamped on, or otherwise applied to the harvest form 100, at the timeof harvesting. In some embodiments, the unique harvest form code 120 isprovided in a human-readable format, as shown, or a machine-readableformat, or both. The unique harvest form code 120 can also be stamped orapplied to the harvest form 100 at the time of harvesting.

The harvest form 100 further includes one or more rows 130, where eachrow 130 is intended to receive a pair of labels 140. The labels 140 aredescribed in greater detail with respect to FIG. 2, below. In someembodiments of the harvest form 100, the spaces provided in the rows 130for the labels 140 can each include a pre-printed dummy code 150 that isintended to be covered by the labels 140, but if not covered can be readto show that a label 140 was missing from the space.

FIG. 2 shows the pre-printed label 140 of FIG. 1 according to anexemplary embodiment of the present invention. Each label 140 includes aunique code that can be represented in a human-readable form 210, in amachine-readable form 220, or both. In one embodiment, the unique codein the human-readable form 210 comprises a 24 digit number. The uniquecode in the machine-readable form 220 can comprise a data matrix, asshown, or a GS1 databar code, for example. Each label 140 may alsoinclude a UPC code 230 corresponding to the produce to be harvested. Insome embodiments, the unique code in the machine-readable form 220 cancomprise both the UPC code 230 and the unique code. Labels 140 can beprovided on rolls or sheets, for example. Further detail regarding theuse of the labels 140 and the unique codes are provided below withrespect to FIG. 3.

FIG. 3 provides a flowchart representation of a method 300 forassociating information with harvested produce according to an exemplaryembodiment of the present invention. The method 300 comprises a step 305of generating a batch of unique codes and a step 310 of producing aplurality of labels 140 including the unique codes generated in step305. The method 300 also comprises a step 315 of recording harvestinformation on a harvest form 100, a step 320 of affixing labels 140 toboth the harvest form 100 and to produce being harvested, and a step 325of associating harvest information with unique codes in a searchabledatabase.

In various embodiments, steps 305 and 310 are performed by a first partythat supplies labels 140 and harvest forms 100, while steps 315, 320,and 325 are performed by a second party, such as a produce grower orpacker, which receives the labels 140 and the harvest forms 100 from thefirst party. In some of these embodiments, the labels 140 and harvestforms 100 are custom made for the second party upon request. Also insome embodiments, the first party produces the harvest forms 100 and/orthe labels 140 at the work site of the second party through a securecomputing system. In still other embodiments, each of the steps 305-325of the method 300 are performed by the same party. It is noted steps 315and 320 can occur in either order or can be performed together.

Step 305 of the method 300 comprises generating one or more batches ofunique codes. A batch of unique codes is a plurality of codes thatfollow a sequence or pattern, or a plurality of codes that are theencryptions of other codes that follow a sequence or pattern. Forclarity, in those embodiments in which the unique codes comprise theencryptions of other codes, the codes that are related to one anotherand that are encrypted are referred to herein as plain text codes whilethe encryptions thereof may be referred to herein as either unique codesor cipher text codes. An exemplary batch of unique codes can comprise,for example, a sequence of serial numbers that have been encrypted.Methods for generating plain text codes and for generating unique codestherefrom are described in detail in related U.S. patent applicationSer. No. 11/619,747 noted above.

It is noted that generating unique codes that are cipher texts and thatinclude large numbers of digits provides certain advantages. Where thenumber of digits is 12, for example, the total possible number of uniquecodes is 10 to the power of 12, thus, the total number of unique codesever in use will be a small fraction of the total possible number ofunique codes. It is therefore unlikely that a person would be able toguess a valid unique code. The unpredictability of the unique codes canbe important for vendor promotions, for example, when there is avaluable benefit, such as a coupon, provided when a customer submits avalid unique code or is reimbursed for poor product quality or arecalled product. If the unique code was predictable, customers couldattempt to defraud the system by guessing codes for units of producethat they had not purchased and obtain the coupons. Furthermore, whenthe set of valid unique identifiers comprises a small fraction of thetotal possible number of unique codes, it is much less likely thatsomeone will submit an unintended, yet valid unique code by mistyping avalid unique code.

In various embodiments, the number of unique codes in a batch isdictated by the needs of the grower or packer. For instance, a batch caninclude a larger number of unique codes to accommodate a large lot size,or a small number of unique codes to accommodate a small lot size. Insome instances, step 305 includes receiving a request for a batch size,for example, a request for a batch of 1,000. The request can come from aproduce grower or packer, for instance. It will be appreciated thattailoring batch size to lot size can be convenient in some instances,but that there is no requirement that they be the same. Accordingly, thebatch size can be much greater or smaller than the lot size.

Step 310 comprises producing a plurality of labels 140 where each label140 includes one of the unique codes from the batch generated in step305. The plurality of labels 140 produced in step 310 can comprise oneor more rolls of labels 140 or a number of sheets of labels 140, forexample. On a roll of labels 140, the unique codes on successive labels140 either follow a sequence or pattern or are the cipher texts of plaintext codes that follow the sequence or pattern. In the latter instance,the unique codes on successive labels 140 on a roll will appear to berandom, but when decrypted will result in plain text codes that followthe sequence or pattern. The same can be applied to the unique codes ofsuccessive labels 140 on sheets of labels 140.

Step 315 comprises recording harvest information on a harvest form 100.The harvest information can be recorded by a harvest supervisor, forinstance. Harvest information can include, for example, the ranch orfarm, the field and section harvested, the crew harvesting the produce,the harvest time and date, the weather conditions, the lot number, typeof produce harvested, brand name, seed variety, special notes, and soforth. As provided above, some of this information may not vary and canbe pre-printed on the harvest form 100.

Step 320 of method 300 comprises affixing labels 140 to both the harvestform 100 and to produce being harvested. Here, “produce being harvested”refers to either loose bulk produce or item-level packaging filled withproduce. In some embodiments, field workers are provided with rolls oflabels 140. Each time a roll of labels 140 is used by a field worker,the field worker peels a first label 140 off of the roll and affixesthat label 140 to a row 130 of the harvest form 100. In the exemplaryharvest form 100, the first label 140 is placed in the left column ofthe harvest form 100. The field worker then affixes successive labels140 from the roll or sheet to produce being harvested. Each loose bulkproduce item or item-level packaging of produce receives one label 140in step 320.

When the field worker reaches the end of a roll, the field worker takesthe final label 140 of the finished roll and affixes that last label 140to the same row 130 of the harvest form 100, such as the right column inthe illustrated example. Similarly, if the field worker has finishedpacking produce in the harvest associated with the particular harvestform 100 but still has a partially used roll, the field worker takes thenext unused label 140 from the partially used roll, and affixes thatlabel 140 to the same row 130 of the harvest form 100. Where the roll isonly partially used, the same roll can be used again with the sameharvest form 100 or with a different harvest form 100. Where a fieldworker finishes a roll before completing the harvest associated with theharvest form 100, the field worker can continue with a new or apartially used roll, again by affixing a first label 140 to the harvestform 100, affixing successive labels 140 to produce being harvested, andthen affixing a last label 140 to the harvest form 100. It will beappreciated that method 300 does not require the same person to performall of the tasks of the step 320. For instance, a field supervisor canaffix the first labels 140 to the harvest form 100 before providing therolls to the field workers.

Step 325 comprises creating a record that associates the harvestinformation recorded on the harvest form 100 with one or more pairs ofunique codes and/or any plain text codes that correspond to the uniquecode pairs. The record can be created with logic, such as a databaseapplication, and stored in a searchable database, for example. Creatingthe record can include, in some embodiments, manually entering theharvest information through a graphical user interface. In some otherembodiments, creating the record can include automatically entering theharvest information with a reader configured to read the harvest form100, such as by recognizing marked checkboxes, decoding barcodes, orperforming optical character recognition, for example. In someembodiments, step 325 also comprises associating the unique harvest formcode 120 with the created record.

FIG. 4 illustrates a graphical user interface 400 for entering harvestinformation, according to an exemplary embodiment of the presentinvention. The graphical user interface 400 can comprise a web pageviewed with a web browser on the display of a personal computer, forinstance. In some embodiments, the web page is served by a remote serverand the record created in step 325 is created and stored remotely. Insome of these embodiments, a party other than the grower or harvestermaintains the created records as a service. The remote server can be ahost in a host-client relationship with a client computing system usedto enter the harvest data.

It can be seen in the exemplary graphical user interface 400 that theharvest information can be automatically entered by reading the harvestform 100, as previously noted. It can also be seen that the graphicaluser interface 400 allows a user to manually enter missing data, orcorrect erroneous data. In various embodiments, pairs of unique codes onthe harvest form 100 are manually entered through a graphical userinterface or automatically entered with a fixed or handheld scanner suchas a barcode reader, for instance. The exemplary graphical userinterface 400 of FIG. 4 shows pairs of unique codes that were enteredautomatically. In some embodiments of the graphical user interface 400,unique codes that were erroneous entered can be selected and removed.

In some embodiments, the unique codes are cipher texts of plain textcodes, as illustrated in FIG. 4, and in these embodiments step 325 canfurther comprise decrypting the unique codes and associating theresulting plain text codes with the record. The further step ofdecrypting the unique codes and associating the resulting plain textcodes with the record can be performed at the time the record is createdor at some later time. For example, in some embodiments the recordassociating the harvest information and the pairs of unique codes iscreated locally, then the record is communicated to a remote computingsystem, such as the remote web server mentioned above, that isconfigured to perform the decryption, save the plain text codes to therecord, and save the record in a searchable database. In someembodiments of the method 300, records created in step 325 onlyassociate the plain text codes with the harvest information, and do notretain the unique codes themselves. In either case, given a unique code,the corresponding harvest information can be readily determined from therecords.

FIG. 5 provides a flowchart representation of a method 500 forassociating information with harvested produce according to an exemplaryembodiment of the present invention. The method 500 comprises the step305 (FIG. 3) of generating a batch of unique codes and a step 510 ofmarking a plurality of item-level packages with the unique codes. Themethod 500 further comprises a step 515 of providing a box packed withthe marked item-level packages and further comprising a unique box code.The method 500 also comprises a step 520 of creating a record thatassociates the unique box code with the marked item-level packageswithin the box. In some embodiments, the steps just described areperformed by a first party that supplies item-level packaging, while thefollowing steps of the method 500 are performed by a second party suchas a grower or harvester. Accordingly, method 500 also comprise a step315 (FIG. 3) of recording harvest information on a harvest form 100, astep 525 of packing the marked item-level packages with produce, and astep 530 of creating a record that associates the unique box code withthe harvest information. Steps 305 and 315 in the method 500 can both beperformed as described above with respect to FIG. 3. Steps 515 and 520can be performed in either order or together, in various embodiments.

Step 510 comprises marking a plurality of item-level packages with theunique codes generated in step 305 to produce a plurality of markeditem-level packages. The item-level packages can comprise bags,clamshells, cartons, baskets, and the like. The item-level packages canbe marked with labels such as label 140, or by various printingtechniques, or by laser engraving, for example.

Step 515 comprises providing a box including the marked item-levelpackages and further comprising a unique box code. Here, the unique boxcode is a unique code assigned to the box and marked on the exterior ofthe box. The unique box code can be marked with a label that includesthe unique box code, or by various printing techniques, or by laserengraving, for example. The unique box code is machine-readable, in someembodiments. Step 515 can include packing the box with some or all ofthe marked item-level packages produced in step 510. It will beunderstood that the marked item-level packages produced in step 510 canbe distributed across many such boxes so long as the unique codes on theitem-level packages within a particular box, or the underlying plaintext codes if the unique codes are cipher texts, follow the series orpattern.

Step 520 comprises creating a record that associates the unique box codewith the marked item-level packages within the box. The record can becreated with logic such as a database application and the record can bestored in a searchable database, for example. Step 520 can compriseentering the unique box code and entering the unique codes from thefirst and last item-level packages placed in the box. Entering theunique box code can be performed manually through a graphical userinterface similar to the graphical user interface 400, or automaticallywith a fixed or handheld scanner, for instance. Likewise, entering thefirst and last unique codes from the marked item-level packages can beperformed automatically by scanning the unique codes or manually througha graphical user interface. Further disclosure regarding packing boxeswith marked item-level packaging can be found in U.S. Provisional PatentApplication No. 61/080,121 filed on Jul. 11, 2008 and entitled “MobileTable for implementing Clamshell-to-Case Association” which isincorporated herein by reference.

In step 520, creating the record that associates the unique box codewith the marked item-level packages within the box can comprise, in someembodiments, associating the unique box code with the first and lastunique codes marked on the item-level packages in the box. In otherembodiments, creating this record comprises associating the unique boxcode with the plain text codes that correspond to the first and lastunique codes marked on the item-level packages.

Step 525 comprises packing the marked item-level packages with produce.Step 525 can be performed manually or through the use of automatedpacking equipment, for example. The filled item-level packages can thenbe aggregated into trays or cases for distribution through the supplychain to the retailer.

Step 530 comprises creating a record that associates the unique box codewith the harvest information from the harvest form 100 recorded in step315. The record can be created with logic such as a database applicationand the record can be stored in a searchable database, for example. Asabove, the record can be created and stored remotely. While the recordscreated in steps 520 and 530 can be created by different logic andstored in different databases, in various embodiments these records arecreated by the same logic and/or stored in the same database.

In some embodiments, step 530 includes writing the unique box code onthe harvest form 100. Later, the record can be created by manually orautomatically entering the harvest information and the unique box codein a manner analogous to that described above with respect to step 325.In further embodiments, the unique box code and the unique harvest formcode 120 are both scanned in the field to create a record thatassociates the two. Later, a record is created with the harvestinformation by manually or automatically entering the harvestinformation in a manner analogous to that described above with respectto step 325, and the unique harvest form code 120 is used to find theassociated unique box code so that the unique box code can be associatedwith the record of the harvest information.

FIG. 6 shows a pre-printed box label 600 according to an exemplaryembodiment of the present invention. The box label 600 facilitates theassociation of unique box codes with harvest information in someembodiments, as described below with reference to FIG. 7. The box label600 can include an adhesive backing and comprises several fields ofinformation including the unique box code 610, which in the illustratedembodiment is presented in both human-readable and machine-readableforms, though either one of these formats can be sufficient. The boxlabel 600 also comprises one or more detachable tags 620 that also eachcomprise the unique box code 610. The detachable tags 620 can beadhesive-backed, in some embodiments. In the illustrated embodiment, thedetachable tags 620 can be peeled off of the box label 600, while inother embodiments the detachable tags 620 can be separated from the boxlabel 600 along perforations, for example. It will be appreciated thatan exemplary box label for the method 500 of FIG. 5 would be box label600 without the detachable tags 620. In some of those embodiments, thebox label can be printed or laser engraved directly onto boxes.

FIG. 7 provides a flowchart representation of another method 700 forassociating information with harvested produce according to an exemplaryembodiment of the present invention. The method 700 differs from themethod 500 in that method 700 is specifically directed to thoseembodiments in which the box label 600 includes the detachable tags 620.Accordingly, method 700 includes a step 710, in place of step 515, inwhich a box is provided including the marked item-level packages andfurther comprising a label 600 including a unique box code and one ormore detachable tags 620 each including the unique box code.Additionally, the method 700 includes the additional step 720 comprisingdetaching a detachable tag 620 from the label 600 and affixing the tag620 to the harvest form 600.

After step 720, the step 530 comprises creating a record that associatesthe unique box code with the harvest information by manually orautomatically entering the harvest information from the harvest form 100and the unique box code from the tag 620 on the harvest form 100,essentially as described above with respect to the method 500.

It will be appreciated that according to the method 700, multipleharvest forms 100 can include tags 620 with same unique box code leadingto the creation of multiple records in step 530 in which potentiallydifferent harvest information becomes associated with the same uniquebox code. As a result, if the records are searched for a particularunique code, several matching records may be found. This is referred toas over-association, and in some situations over-association isadvantageous.

For example, when investigating a food contamination situation, while itmay not be possible in these embodiments to know which of the severalrecords found for a particular unique code is the correct record of theharvest for that unique code, it is useful to know that several harvestsmight be closely related and each harvest is worth furtherconsideration. Additionally, when a consumer requests harvestinformation for a particular unit of produce, several harvest recordsmay be returned. However, in most instances the several records will befor harvests all within a general vicinity, within a short period oftime, and under very similar conditions.

It should be noted that the harvest information records created inmethods 300, 500, and 700 can be updated with additional information notprovided on the harvest form 100. Weather information is one example,described in greater detail below. Customer satisfaction information,also described in greater detail below, can also be added as it isacquired. Other records, such as those pertaining to chemical andpesticide use on the field, temperature during transportation, anddistribution, for example, can be linked to the harvest informationrecords, as well.

FIG. 8 provides a flowchart representation of optional steps that can beincluded in any of the exemplary methods 300, 500, 700 provided withrespect to FIGS. 3, 5, and 7, according to exemplary embodiments of thepresent invention. More specifically, the steps described with referenceto FIG. 8 can be sub-steps of the step 530 in both methods 500, 700 orof the step 325 in method 300.

In a step 810, a range of plain text codes corresponding to a pair ofunique codes is determined. For example, each of the pair of uniquecodes is decrypted. The decryption can be performed by the same logicthat creates and stores the records, and contemporaneously with creatingand storing the records, in some embodiments. In other embodiments, thepair of unique codes is decrypted by different logic, potentially of adifferent computing system, potentially at a later time, and potentiallyat a remote location. For instance, a record can be created by acomputing system at a field office and then communicated to a morecentralized office, such as a corporate office or to a second party thatprovides product traceability services. These later embodiments offerthe advantage of tighter control over decryption keys and alsocentralized record-keeping. In some instances, the range of plain textcodes excludes those plain text codes that are associated with the pairof unique codes from the first and last labels affixed to the harvestform 100 and not affixed to produce.

In a step 820, errors are detected and fixed. One way in which errorscan be detected is by comparing the ranges between the pairs of uniquecodes, or between the corresponding plain text codes, to the number oflabels 140 on the rolls. For instance, the size of the rolls can beselected so that in most instances the field workers will completely useeach roll during a harvest. For a particular type of produce, forexample, each roll may comprise 1000 labels. In this case, the first andlast unique code in a row 130 on the harvest form 100 will most commonlybe the first and last labels of the roll. When first and last uniquecodes span a range of exactly 1000 labels 140, there is a high degree ofconfidence that the record is accurate.

One error that is readily detected and corrected is where the first andlast labels 140 for a particular roll have been transposed. Here, therange of the unique codes, or of the plain text codes, will bebackwards. If the absolute value of the range equals, or is close to,the number of labels 140 on a roll, then the values can be reversed witha high degree of confidence.

When the range spanned by the first and last unique codes exceeds thenumber of labels 140 on an entire roll, then it is likely that there isan error wherein the first label came from one roll and the last label140 improperly came from another roll. In some embodiments, suchtransposed labels 140 on a harvest form 100 can be readily determinedbecause switching two last labels 140 creates two ranges that eachequals the number of labels 140 on the rolls. In situations wheretransposing labels 140 does not produce two corrected ranges that bothequal the number of labels 140 on a roll, then a degree of confidencecan be determined for various alternatives and the alternative with thehighest degree of confidence can be selected. In some embodiments,finding and correcting errors can consider more than a single harvest tofind labels 140 incorrectly placed on the wrong harvest forms 100.

In other embodiments, such errors are not corrected, over-associatingunique codes with harvest information. This is done on the theory thatit is beneficial to know all the harvest information that may beassociated with a unique code and thereby reliably exclude all otherharvest information as not being associated with the unique code. Insome embodiments, associations of unique codes with a harvest are onlyremoved when the possibility can be positively ruled out. In othercases, only certainty above some lesser confidence threshold is requiredto rule out such an association.

Other methods of the invention pertain to utilizing the records createdin methods 300, 500, and 700. In some embodiments, a unique code isreceived by a host computing system, for example, through a webpageserved by a remote server. The URL for the web site can be printed onthe label 140, for instance. The unique code can come from a customer ata kiosk in a supermarket, a customer using a home computer, a retailer,a distributor, a government agency, a grower, or a harvester, forexample. The unique code can be entered manually by reading thehuman-readable form 210, or by scanning the machine-readable form 220with a barcode scanner, for example. In some cases, the machine-readableform 320 can be imaged using a cell phone camera, or submitted using theShort Messaging Service (SMS) or another mobile phone-basedcommunication service.

In some instances, the type of entity submitting the unique code can bedetermined from an IP address, a login page, etc. Based on the type ofentity, some or all of the harvest data can be made available. Forinstance, a retail customer would have access to information about thelocation of the field, but not the names of workers, the date of theharvest, and so forth. All harvest information, on the other hand, wouldbe accessible to an investigator from the FDA.

Upon receiving the unique code, where the unique code comprises a ciphertext, the host computing system decrypts the unique code to determinethe corresponding plain text code. The records are then searched to finda range of plain text codes that includes the one for the submittedunique code. In some embodiments, the range directly correlates to arecord of harvest information. In other embodiments, the rangecorrelates to a record that associates the range with a unique box code.Here, further records are searched to find those records that correlatethat unique box code with harvest information.

Once the harvest information has been retrieved, that information can beused to ascertain other information. For example, where the harvestinformation includes the location of the field and the date and time ofthe harvest, this information can be used to retrieve weatherinformation at the time of harvest from National Weather Servicerecords. It will be appreciated that such further information need notonly be determined upon a particular request, but can be associated withthe record of the harvest information at the time the record wascreated, or any time thereafter. In some embodiments, weatherinformation for an entire growing season can be associated with theharvest records.

Additionally, once the harvest information has been determined for aparticular unique code, other information can be determined. Forexample, a customer can request an estimate of the “food miles” for theproduce, an estimate of how far the food travelled to reach thecustomer. The customer can enter an address or a zip code to establishone end point, the field of the harvest comprises the other end point,and the distance between can be readily estimated. In some embodiments,travel time from the field to the retailer can be provided or estimated,while in other embodiments this is considered proprietary informationand not made available to the public.

Also, retailers, distributors, growers, and harvesters, for instance,can collect customer satisfaction information from the customers thatsubmit unique codes. The customer satisfaction information can includeinformation collected from the customer, such as the retailer from whichthe produce was purchased, the date the produce was purchased andconsumed, and a satisfaction rating for the quality of the produce.

The customer satisfaction information can then be correlated with theharvest information for the submitted unique code, such as the field theproduce was grown on, the date that the produce was harvested, theretailer that sold the produce, the region that the produce was sold,the time of day the produce was harvested, the weather at the time ofharvest, the transit time from harvest to consumption, and other factorsthat may be related directly or indirectly to customer satisfactionlevels. This information can be analyzed by retailers, for example, toidentify those growers that yield the greatest customer satisfactionlevels, to provide feedback to growers as to the conditions which seemto yield the best results, and to adjust the supply chain to havetransit times with better customer satisfaction levels.

In some embodiments, incentives can be provided to encourage customerparticipation in providing information. For example, promotions,discounts, special offers, and coupons can be offered as incentives.

FIG. 9 provides a flowchart representation of a method 900 forassociating information with harvested produce according to stillanother exemplary embodiment of the present invention. The method 900adds an additional step 910 of marking on labels to the method 300 (FIG.3). The labels used in method 900 are similar to the labels 140 butinclude fields of sufficient size for adding the marking of step 910. Anexemplary such label 1000 is shown in FIG. 10.

Label 1000 includes the same information as label 140, namely, a uniquecode represented in a human-readable form 210 or in a machine-readableform 220, or both, and an optional UPC code 230. Label 1000 alsoincludes blank spaces 1010 and 1020 appropriately sized to later receiveadditional information. Label 1000 optionally also can include a call toaction 1030 and text 1040 that serves to identify at least some of thelater-marked information.

In an exemplary step 910, a lot code 1110 and a date such as a bestbefore date 1120 are both marked on the label 1000, as shown in FIG. 11.Here, the text 1040 identifies the marked characters as a best beforedate. The text 1040 can, in the alternative, indicate a harvest date.Step 910 can comprise marking only one of the lot code 1110, best beforedate 1120, or harvest date, or any combination thereof. The lot code1110 can be, for example, a globally unique code, or, as shown in FIG.11 can be a short code that in combination with a date such as the bestbefore date 1120 or a harvest date is unique. An example of a short codefor the lot code 1110 is a ranch ID.

Marking can be accomplished by printing with a printer or with ahand-held date-coding gun, in some embodiments. Marking with a hand-helddate-coding gun can be performed after each label 1000 is affixed to theproduce in step 320, for example. The same marking is optionally alsoapplied to the labels 1000 after being placed on the harvest form 100,or can be added to the harvest form 100 elsewhere, such as between thelabels 1000.

Marking in step 910 can also be accomplished by printing with a printer.In these embodiments a roll of labels 1000 is fed through a printer toadd the lot code 1110, best before date 1120, and/or harvest date. Thelabels 1000, having been marked, are then affixed to the harvest form100 and to packages of produce in step 320. In still other embodiments alabeling gun holds a roll of labels 1000 and prints the lot code 1110,best before date 1120, and/or harvest date on each label 1000 when thelabel 1000 is applied to a package.

FIG. 12 provides a flowchart representation of a method 1200 forassociating harvest information with harvested produce according to yetanother exemplary embodiment of the present invention. The method 1200includes steps in common with the method 500 (FIG. 5). Both include, forexample, the step 305 of generating a batch of unique codes and the step510 of marking a plurality of item-level packages with the unique codes.Both methods 500 and 1200 also include the step 525 of packing theitem-level packages with produce. In method 500, however, a box code isemployed, whereas in method 1200 there is a step 1210 of filling acontainer with the marked item-level packages and a step 1220 ofcreating a record that associates the marked item-level packages withinthe container to each other.

In step 1220, creating the record that associates the marked item-levelpackages in the container to each other can comprise, for example,associating the marked item-level packages with another unique code suchas the box code noted above. In other embodiments, creating the recordthat associates the marked item-level packages in the container to eachother can comprise simply scanning one or more of the marked item-levelpackages. For example, where the unique codes marked on the item-levelpackages are sequential, scanning the unique codes of the first and lastitem-level packages placed in the container serves to define a range ofunique codes. As another example, if a specific number of item-levelpackages are placed in each container and the unique codes marked on theitem-level packages are again sequential, then one need only scan, forinstance, a first item-level package and that next number of item-levelpackages can be associated with one another. Even if the number ofitem-level packages varies from container to container, if one routinelyscans the first item-level package, for example, then the scanneditem-level package and each item-level package in the sequencethereafter until the next scanned item-level package can be associatedtogether.

Another difference between method 1200 and method 500 is that the step315 in method 500 records harvest information on a harvest form and thenstep 530 creates a record that specifically associates the unique boxcode with the harvest information, while step 1230 of method 1200comprises recording harvest information and associating the harvestinformation to the associated marked item-level packages. Thus, whilerecording harvest information in step 1230 can comprise recording theharvest information on a harvest form, the harvest information can berecorded electronically with one or more hand-held devices, for example.

It will be appreciated, as above, that the steps of marking item-levelpackages, filling containers with the marked item-level packages, andcreating records that associate together the item-level packages withineach container are generally performed by a different party than theparty that records harvest information, packs the marking item-levelpackages with produce, and associates the harvest information with theitem-level packages from each container. A third party may generatebatches of unique codes and supply those codes to the first party, andmay receive from the second party and store in a database harvestinformation associated to ranges of unique codes from the batch. If thethird party receives the ranges assigned to each container back from thefirst party, then the second party only needs to upload the harvestinformation in association with the scanned unique codes, and the thirdparty can associate the harvest information to the appropriate ranges ofcodes. Alternatively, the first party can provide the ranges of codes ineach container to the second party when providing those containers ofempty item-level packaging. In these embodiments, the second partyassociates the ranges with harvest information and uploads the same tothe third party.

Other associations can be made to each associated set of markeditem-level packages. In the above example, a unique code on anitem-level package can be scanned by the second party as part of a labordata collection event to associate an individual or a crew to a numberof item-level packages. The labor data can then be assigned to theharvest information. As another example, a random plurality ofitem-level packages can be scanned as part of a quality inspectionprocess some time after distribution. This step can be performed byfourth parties along the distribution chain such as distributioncenters, warehouses, and retail stores. The time and location of thescanning event, as well as any quality assessments made, can be furtherassociated to the harvest information.

FIG. 13 provides a flowchart representation of a method 1300 forassociating information with harvested produce according to stillanother exemplary embodiment of the present invention. The method 1300comprises a step 1310 of generating a batch of unique codes and storingthe batch, a step 1320 of transmitting the batch, an optional step 1330of printing the batch on a roll of labels, a step 1340 of receiving afirst unique code in association with first harvest data, and a step1350 of storing the first harvest data in association with the batch.The method 1300 optionally also comprises a step 1360 of receiving asecond unique code in association with second harvest data, and a step1370 of storing the second harvest data in association with the secondunique code and the batch. As above, this method can be performed by athird party that generates batches of unique codes and supplies thosebatches to a first party that supplies labels printed with the uniquecodes to second party harvesters; the third party then receives harvestinformation associated to unique codes from the second parties. In thealternative, the third party can both generate the batches and print thelabels, combining the functions of the first and third parties. Bothalternatives are discussed below.

Step 1310 in FIG. 13 comprises generating a batch of unique codes with afirst computing device, the codes spanning a first range from an initialcode to a final code, and storing the batch. Methods of generatingbatches of unique codes, including generating sequences of plain textcodes and encrypting those plain text codes, have been describedpreviously herein. Thus, a batch of unique codes can comprise a sequenceof plain text codes or the encryptions thereof, in various embodiments.Where the batch of unique codes comprises a sequence of plain textcodes, the batch spans a first range from an initial code of thesequence to a final code of the sequence and the range has a lengthdefined by the difference. The length of the sequence, as describedbelow, is equal to the number of labels on a roll of labels. A batch ofunique codes can also comprise the encryptions of a sequence of plaintext codes. In these embodiments, the batch spans a first range from aninitial code, being the encryption of the initial plain text code of thesequence, to a final code, being the encryption of the final plain textcode of the sequence, and the range has a length defined by thedifference between the final and initial plain text codes.

Step 1310 comprises generating the batch of unique codes with a firstcomputing device, such as a server or personal computer. The batch ofunique codes, once generated, is then stored in a database incommunication with the first computing device. Where the batch of uniquecodes comprises a sequence of plain text codes, storing the batch cancomprise storing the initial and final plain text codes, or the initialor final plain text code in conjunction with the length of the sequence,for instance. Where the batch of unique codes comprises the encryptionsof a sequence of plain text codes, storing the batch can comprisestoring the encryption of each unique plain text code of the sequence,or, since the encryption algorithm is known, storing the batch can alsocomprise storing the initial and final plain text codes, or the initialplain text code in conjunction with the length of the sequence.

Step 1320 in FIG. 13 comprises transmitting the batch of unique codes toa second computing device. As noted, this can comprise sending the batchfrom the third party to a first party that supplies harvesters withharvesting supplies like printed labels. In these embodiments,transmitting the batch can comprise any known secure method for datatransmission including those employing the Internet and telephonicsystems, as well as writing to a portable storage medium like a compactdisk and sending the storage medium by courier. In other embodiments thefirst computing device may simply transmit the batch in step 1320 to alocal second computing device over a local area network (LAN), forexample. In either instance the second computing device can be a labelprinting device or a computing device that controls a label printingdevice. Transmitting the batch can comprise transmitting each uniquecode thereof, such as when the unique codes are encryptions of plaintext codes, or transmitting the initial plain text code and final plaintext code, in various embodiments. Transmitting the batch can alsocomprise transmitting just the initial plain text code where the numberof labels per roll is fixed, for example, and the second computingsystem is configured to print sequentially starting with the initialplain text code.

Step 1330 in FIG. 13 comprises the optional step of printing a roll oflabels, where each label of the roll is sequentially printed with adifferent unique code from the batch. The initial label of the roll,being the first label a person would remove from the roll, is printedwith the initial unique code of the batch, and each label thereafter isprinted with the next sequential unique code until the final label ofthe roll receives the final unique code of the batch. In some instances,the printing process itself begins with the final label and incrementsto the initial label.

Step 1340 comprises receiving a first unique code in association withfirst harvest data from a third computing device. As noted, the thirdcomputing device can be that of a harvester that has used a roll oflabels while harvesting produce, for example. Corresponding methods ofthe harvester are discussed below, with respect to FIG. 14. The firstunique code and the first harvest data can be received over a secondcommunication channel, such as those noted regarding the firstcommunication channel. Where the same party generates the batch in step1310 and performs a method according to FIG. 14, the secondcommunication channel could be a LAN. In some embodiments, the harvestdata that is received comprises a link or pointer to a database entry ofsuch information, rather than the information itself.

Step 1350 comprises storing the first harvest data in association withthe batch of unique codes. This can comprise, for instance, creating arecord in a database or adding to the existing record for the batch ofunique codes that was established in step 1310. In either event, step1350 includes searching that latter database to determine which range ofunique codes, and thus which batch, the received first unique codebelongs. This can include the step of decrypting the first unique codein those instances where the unique codes are encryptions of plain textcodes. Storing harvest data in association with the batch of uniquecodes can be accomplished by storing a link or pointer in a field of thedatabase record for the batch, or by including sufficient individualfields for such data in each database record. The received first uniquecode can also be stored in association with the first harvest data andthe batch in step 1350.

In some instances, the first unique code is the initial unique code froma roll, such as when an unused roll is first used, and the initial labelis removed and applied to a harvest form (see FIGS. 5 and 6). In otherinstances the first unique code is some subsequent unique code from thebatch. In either situation the assumption is made that the entire rollof labels was used in association with the received harvest event data,and one label at random was selected from the roll to make theassociation. This can happen, where, for example, a hand-held device isused to read unique codes from labels that have been applied to produceor unit packages.

It will be appreciated that in embodiments where a hand-held device isemployed to make associations between unique codes and harvest data (seeFIG. 14), step 1340 may comprise receiving multiple instances of uniquecodes each paired with the same first harvest data, and step 1350 caninclude storing each such unique code in association with the firstharvest event data and batch. In some of these embodiments, eachinstance of a pairing of a unique code and harvest data received in step1340 also is received with a time stamp and or a location representingthe time and/or place where the pairing was made.

Step 1360 comprises receiving a second unique code in association withsecond harvest data from the third computing device, as in step 1340.Step 1370 comprises storing the second harvest data in association withthe second unique code and the batch, as in step 1350.

Pairings of harvest data with unique codes from labels on the same roll,and hence the same batch, may be received in any order, as for example,if rolls of labels are unwound, torn into long strips, and distributedto pickers heading into different fields or blocks. Also, where labelsare applied to harvest forms, as discussed with respect to FIGS. 14-16,the harvest forms can be later read and the information uploaded innon-sequential order.

Furthermore, more than one set of harvest data can be associated withone batch, such as when strips from a roll are distributed or apartially used roll is used in a different harvest event, in which casethe result is over-association, noted earlier. Additionally, aninference can be made that any unique code in the sequence of a batchthat follows a received unique code associated with some harvest data isalso to be associated with the same harvest data because there is onlyone way to conveniently remove labels from a roll, and because theunique codes are sequential, or are encryptions of sequential plain textcodes.

FIG. 14 provides a flowchart representation of a method 1400 forassociating information with harvested produce according to stillanother exemplary embodiment of the present invention. The method 1400comprises a step 1410 of receiving a roll of labels, a step 1420 ofassociating first harvest data with a first unique code, a step 1430 ofaffixing labels from the roll, and a step 1440 of transmitting the firstunique code in association with the first harvest data. Optionally, themethod 1400 further comprises a step 1450 of associating second harvestdata with a second unique code and a step 1460 of transmitting thesecond unique code in association with the second harvest data.

With additional reference to FIG. 15, step 1410 of method 1400 comprisesreceiving a roll 1500 of labels 1510, where each label 1510 of the roll1500 sequentially includes a unique code 1520 from a batch of uniquecodes, the unique codes 1520 spanning a range from an initial uniquecode to a final unique code, an initial label 1530 of the roll 1500including the initial unique code and a final label (not shown) of theroll 1500 including the final unique code. The unique codes 1520 can beprinted in both human-readable and machine-readable formats, asillustrated. The label backing layer 1540 can be printed with useinstructions, as shown, to help where strips of labels 1510 are removedfrom the roll 1500, for example.

Returning to FIG. 14, step 1420 comprises associating first harvest datawith a first unique code 1520 of a label 1510 of the roll 1500. In someinstances a picker may employ a hand-held device such as the oneillustrated in U.S. patent application Ser. No. 12/908,667 filed on Oct.20, 2010 entitled “Methods for Correlating First Mile and Last MileProduct Data,” incorporated herein by reference, and adapted to enterharvest data and to read unique codes 1520. In these embodiments,associating first harvest data with a first unique code 1520 comprisesentering harvest data into the hand-held device and reading a uniquecode 1520 from a label 1510. In some embodiments the hand-held device isconfigured to lead a picker through the steps needed to make theassociation by prompting for the harvest information then prompting thepicker to read a label 1510. In some embodiments, and with reference tostep 1430, the hand-held device is configured to wirelessly transmit theharvest data and unique codes 1520 to the computing device that receivesthe same in step 1340 of method 1300. In other instances, the hand-helddevice stores the harvest data in association with the read unique codes1520 until docked to another computing device that transmits the same.As noted previously, the hand-held device can add a time stamp and/orlocation coordinates to records associating harvest data and uniquecodes 1520.

In other embodiments, associating first harvest data with a first uniquecode 1520 of a label 1510 in step 1420 comprises removing the label 1510from the roll 1500 and affixing the label 1510 to a harvest form such asharvest form 1600 of FIG. 16. Like harvest forms 100 and 600 describedpreviously herein, a picker can record harvest data on the harvest form1600 and affix labels 1510 thereto as each new roll 1500, or stripthereof, is put into use. Ideally, one affixes the initial label 1530 ofthe roll 1500, or the first label 1510 of a strip, to the harvest form1600, but any label 1510 can suffice. Step 1420 in these embodimentsfurther comprises transferring the harvest data and the unique codes1520 from the labels 1510 on used harvest forms 1600 to electronicrecords and, in step 1430, transmitting these records to the computingdevice that receives the same in step 1340 of method 1300, as generallydescribed elsewhere herein.

Step 1440 of method 1400 comprises affixing labels 1510 from the roll1500 to item-level packages or individual items of produce (e.g.,squashes and melons), as described generally with respect to step 320 ofmethod 300 (FIG. 3). It will be appreciated that although step 1440follows step 1430, in some embodiments labels 1510 are affixed in step1440 before harvest data and unique codes 1520 are transferred fromharvest forms 1600 and transmitted in step 1430.

In some instances a roll 1500 may be only partially used with respect toa particular harvest event. Partially used rolls 1500 can be used withsubsequent harvest events, and in these embodiments method 1400 furthercomprises the step 1450 of associating second harvest data with a secondunique code 1520 from the roll 1500, and the step 1460 of transmittingthe second unique code 1520 in association with the second harvest data.These steps, and the step of affixing labels, are repeated as describedwith respect to steps 1420-1440 until the roll 1500 is depleted.

Computing systems referred to herein can comprise an integrated circuit,microprocessor, a personal computer, a server, a distributed computingsystem, a communication device, a network device, or the like, andvarious combinations of the same. A computing system may also comprisevolatile and/or non-volatile memory such as random access memory (RAM),dynamic random access memory (DRAM), static random access memory (SRAM),magnetic media, optical media, nano-media, a hard drive, a compact disk,a digital versatile disc (DVD), and/or other devices configured forstoring analog or digital information, such as in a database. Thevarious examples of logic noted above can comprise hardware, firmware,or software stored on a computer-readable medium, or combinationsthereof. Computer-implemented steps of the methods noted herein cancomprise a set of instructions stored on a computer-readable medium thatwhen executed cause the computing system to perform the steps. Acomputer-readable medium, as used herein, specifically excludes carrierwaves.

In the foregoing specification, the invention is described withreference to specific embodiments thereof, but those skilled in the artwill recognize that the invention is not limited thereto. Variousfeatures and aspects of the above-described invention may be usedindividually or jointly. Further, the invention can be utilized in anynumber of environments and applications beyond those described hereinwithout departing from the broader spirit and scope of thespecification. The specification and drawings are, accordingly, to beregarded as illustrative rather than restrictive. It will be recognizedthat the terms “comprising,” “including,” and “having,” as used herein,are specifically intended to be read as open-ended terms of art.

What is claimed is:
 1. A method comprising: generating a batch of uniquecodes with a first computing device, the codes spanning a first rangefrom an initial code to a final code, and storing the batch of uniquecodes in a database; transmitting the batch of unique codes to a secondcomputing device; receiving a first unique code in association withfirst harvest data from a third computing device after transmitting thebatch of unique codes to the second computing device; and storing thefirst harvest data in association with the batch of unique codes in thedatabase.
 2. The method of claim 1 wherein the second computing devicecomprises a label printing device.
 3. The method of claim 1 furthercomprising printing a roll of labels, each label of the rollsequentially printed with a different unique code from the batch, fromthe initial label of the roll with the initial unique code to the finallabel of the roll with the final unique code.
 4. The method of claim 3wherein the unique codes printed on the labels are printed in both ahuman-readable format and a machine-readable format.
 5. The method ofclaim 1 wherein transmitting the batch of unique codes to the secondcomputing device is performed over a first communication channel.
 6. Themethod of claim 5 wherein receiving the first code in association withthe first harvest data from the third computing device is performed overa second channel.
 7. The method of claim 1 further comprising receivinga second code in association with second harvest data from the thirdcomputing device, and storing the second harvest data in associationwith the batch of unique codes in the database.
 8. A method comprising:receiving a roll of labels, each label of the roll sequentiallyincluding a unique code from a batch of unique codes, the unique codesspanning a range from an initial unique code to a final unique code, aninitial label of the roll including the initial unique code and a finallabel of the roll including the final unique code; associating firstharvest data with a first unique code from a label of the roll; affixinglabels from the roll to item-level packages or individual items ofproduce; and transmitting the first unique code in association with thefirst harvest data.
 9. The method of claim 8 wherein associating thefirst harvest data with the first unique code includes reading the firstunique code with a hand-held device.
 10. The method of claim 8 whereinassociating the first harvest data with the first unique code includesaffixing a label from the roll to a harvest form, the label includingthe first unique code.
 11. The method of claim 8 further comprisingassociating second harvest data with a second unique code from the roll,and transmitting the second unique code in association with the secondharvest data.